Drivers license parser

ABSTRACT

A driver&#39;s license parser including: a data accessor configured for accessing data from a scanned bar code of a driver&#39;s license of a customer; a data parser configured for parsing the data to achieve parsed data, wherein the parsed data represents a customer profile of the customer; a parsed data storer configured for causing the parsed data to be stored; a comparer configured for comparing the parsed data with requirements of a loyalty program enrollment policy to determine what information of the parsed data falls within the loyalty program enrollment policy; a customer profile validity determiner configured for, based on the comparing, determining a validity of the customer profile; and a form populator configured for, if the customer profile is determined to be valid, populating at least one form with the parsed data to achieve at least one populated form.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and benefit of co-pending U.S.Patent Application No. 61/947,360, filed on Mar. 3, 2014 entitled“DRIVERS LICENSE PARSE[R]” by Tim Pontious, having Attorney Docket No.ADS-064.PRO, and assigned to the assignee of the present application.

BACKGROUND

Certain inefficiencies exist when it comes to a consumer filling outforms, such as medical documents, credit card applications, employmentapplications, loyalty program applications, and the like. The consumerspends an inordinate amount of time filling out the forms and themerchant spends valuable time retyping some of the information from theforms into yet more computer-generated forms. Further inefficienciesresult when, after the form is filled out, the consumer is turned downfor such things as the extension of credit and employment.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form a part ofthis specification, illustrate various embodiments and, together withthe Description of Embodiments, serve to explain principles discussedbelow. The drawings referred to in this brief description should not beunderstood as being drawn to scale unless specifically noted.

FIG. 1 is a block diagram that illustrates an embodiment of a driver'slicense parser, in accordance with an embodiment.

FIG. 2 is a block diagram that illustrates an embodiment of a systemincluding a driver's license parser, in accordance with an embodiment.

FIG. 3 depicts a flow diagram for a method for automatically populatinga form using scanned information from a bar code of a driver's license,in accordance with an embodiment.

FIG. 4 is a block diagram of an example computer system with which orupon which various embodiments of the present invention may beimplemented.

SUMMARY

The following is a summary of at least one embodiment of the presenttechnology:

An article of manufacture, which includes a computer readable mediumhaving stored therein a computer program for automatically populating aform using information from a scanned bar code of a driver's license isdescribed herein. The computer program includes: a first code segmentwhich, when executed on a computer, accesses data from a scanned barcode of a driver's license of a customer; a second code segment which,when executed on the computer, parses the data to achieve parsed data,wherein the parsed data represents a customer profile of the customer; athird code segment which, when executed on the computer, causes theparsed data to be stored; a fourth code segment which, when executed onthe computer, compares the parsed data with requirements of a loyaltyprogram enrollment policy to determine what information of the parseddata falls within the loyalty program enrollment policy; a fifth codesegment which, when executed on the computer, based on the comparing,determines a validity of the customer profile; and a sixth code segmentwhich, when executed on a computer, if the customer profile isdetermined to be valid, populates at least one form with the parsed datato achieve at least one populated form.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to various embodiments, examples ofwhich are illustrated in the accompanying drawings. While variousembodiments are discussed herein, it will be understood that they arenot intended to be limiting. On the contrary, the presented embodimentsare intended to cover alternatives, modifications and equivalents, whichmay be included within the spirit and scope the various embodiments asdefined by the appended claims. Furthermore, in this Description ofEmbodiments, numerous specific details are set forth in order to providea thorough understanding. However, embodiments may be practiced withoutone or more of these specific details. In other instances, well knownmethods, procedures, components, and circuits have not been described indetail as not to unnecessarily obscure aspects of the describedembodiments.

Notation and Nomenclature

Unless specifically stated otherwise as apparent from the followingdiscussions, it is appreciated that throughout the present Descriptionof Embodiments, discussions utilizing terms such as “accessing,”“parsing”, “storing”, “comparing”, “determining”, “populating”,“sending”, “generating”, or the like, often refer to the actions andprocesses of an electronic computing device (or portion thereof), moduleor system, such as, but not limited to, a driver's license parser (SeeFIGS. 1 and 2). The electronic computing device/module/system transmits,receives, stores, manipulates and/or transforms signals represented asphysical (electrical) quantities within the circuits, components, logic,and the like, of the electronic computing device/system into othersignals similarly represented as physical electrical quantities withinthe electronic computing device/system or within or transmitted to otherelectronic computing devices/systems.

The following definitions apply:

“Client”: A retail partner of the system described herein forautomatically populating a form using information from a scanned barcode of a driver's license.

“Client System”: The client's Point of Service system.

“Customer”: The client's consumer/customer.

“Customer Facing Device”: A device that allows direct interaction orcommunication with customers (such as a signature capture, pin paddevice, or bar code scanner).

“Driver's License”: The term, “driver's license”, includes anygovernment issued identification. For example, but not limited to suchexample, a government issued identification may refer to a state issueddriver's license, a state identification, a military identification, afederal identification, a locally-issued identification, a province inCanada, etc. The government issued identification may be issued by anygovernmental authority.

“Points of Service”: Any channel where a transaction can be processedfor a customer (i.e., Catalog, Web, Retail, Mobile).

SSN”: Any governmentally assigned social security number (e.g., UnitedStates, Canada, etc.).

Overview of Embodiments and Discussion

Certain inefficiencies exist when it comes to filling out forms, such asmedical documents, credit card applications, employment applications,loyalty program applications, and the like. Further inefficienciesresult, when after the form is filled out, the consumer is turned downfor such things as the extension of credit and employment. Embodimentsprovide a way for consumers to be screened before such forms are filledout and for these forms to be efficiently completed without the time andexpense to both the consumer and the merchant.

The following is a high-level non-limiting example of embodiments. Afishing store located in Montana asks Fred if he would like to beconsidered for their loyalty program. Fred decides that he would like toreceive the member benefits of a loyalty program. The store clerk takesFred's driver's license and scans the bar code. The driver's licenseparser described herein will determine if the information appearing onthe bar code of Fred's driver's license fits within the restrictionsdictated by the fishing store. In order to offer the loyalty card forthe loyalty program, the fishing store's only restriction is that theresidence of the customer who receives the loyalty card must be in thestate of Montana. The “customer profile validity determiner” of theinvention determines that Fred's address is in fact in the state ofMontana, and therefore, Fred's profile meets the restrictions and istherefore valid. The driver's license parser will then automaticallypopulate the loyalty program form with Fred's personal informationgarnered from the driver's license scanned bar code data. For example,the driver's license parser inserts Fred's address and driver's licensenumber into the loyalty program form. Thus, embodiments provide a methodfor automatically populating a form using scanned information from a barcode of a driver's license, thereby reducing the inefficiencies of aconsumer and/or merchant manually filling out forms with the consumer'sinformation. Further, since the driver's license parser is enabled to“screen’ a consumer to make sure that the customer's profile is withinthe restrictions before forms are filled out, further inefficiencies areavoided.

The following discussion will begin with a description of a driver'slicense parser, with reference to FIGS. 1 and 2. The discussion willfollow with a description of a method of operation for automaticallypopulating a form using information from a scanned bar code of adriver's license, with reference to FIGS. 1-3. The discussion concludeswith a description of an example computer system with which or uponwhich various embodiments of the present technology may be implemented.

Embodiments of a Driver's License Parser

FIGS. 1 and 2 depict block diagrams that illustrates an embodiment of adriver's license parser 100 and a system 200 that includes the driver'slicense parser 100. The driver's license parser 100 includes thefollowing modules coupled with a computer: a data accessor 105; a dataparser 110; a parsed data storer 115; a comparer 120; a customer profilevalidity determiner 125; and a form populator 130. In various optionalembodiments, the driver's license parser 100 further includes a formsender 170; a loyalty program savings offer generator 175; and an offersender 180. The form populator 130 optionally includes a loyalty formprogram populator 135 and a credit account form populator 140.

FIG. 1 further depicts the driver's license parser 100 coupled with, viawire and/or wirelessly, the bar code scanner 185 and the client 155. Inone embodiment, the client 155 includes a point of service (POS) station160. The client 155 controls the forms that are filled out. While thediscussion herein is focused on populating loyalty program forms andcredit account application forms, it should be appreciated that theconcepts herein may be applied to filing in other types of forms usingthe scanned bar code of a driver's license, such as, but not limited to,medical forms and employment applications. It should also be appreciatedthat the POS station 160 may be located somewhere other than at theclient 155. It should also be appreciated that a customer may possessthe scanning technology (e.g., tablet with an integrated bar codescanner), wherein the customer is positioned remotely from the client.

The data accessor 105 is configured for accessing (i.e., receiving orretrieving) data from a scanned bar code of a driver's license of acustomer. The data accessor 105 may either, via wire and/or wirelessly,receive the scanned bar code data from the receiver 205 (see FIG. 2) orretrieve the scanned bar code data from the receiver 205. In oneembodiment, the client 155 is operating the bar code scanner 185. Forexample, the client 155 may be a retailer that is communicativelycoupled with the driver's license parser 100. The store associate at theretail store is operating the POS station 160 and is also providing, foruse to customers, the bar code scanner 185.

In another embodiment, the driver's license parser 100 accesses thescanned bar code data from a third party that is operating a bar codescanner 185, wherein the third party and the driver's license parser 100are communicatively coupled. In another embodiment, the driver's licenseparser 100 accesses the scanned bar code data from the third party,which itself had accessed the scanned bar code data from the bar codescanner 185 that is located at a location other than the third party andthe driver's license parser 100. It should be appreciated that the“third party” may be any entity other than the driver's license parser100, the server 190, and the client 155.

The data parser 110 is configured for parsing the data accessed from thescanned bar code to achieve the parsed data 125. The term “parsing”refers to breaking the scanned bar code data into smaller chunks byfollowing a set of rules, so that it can be more easily interpreted,managed, or transmitted by a computer. The data parser 110 breaks thescanned bar code data into smaller chunks, according to a set ofpreprogrammed set of rules relating to, but not limited to, any of thefollowing topics: the address appearing on the driver's license; the ageof the driver's license owner; the weight and/or height of the driver'slicense owner; the driver's license number; the expiration date of thedriver's license owner; and the birthdate of the driver's licenseholder. These “chunks” are translated into a digital form such that theymay be used to automatically populate various forms and transmitted to aclient. Additionally, the process of “parsing” is commonly known tothose knowledgeable in the field of technology.

The parsed data storer 115 is configured for causing the parsed data 112to be stored. This storage may occur at the memory store 145 located atthe driver's license parser 100, in one embodiment. In anotherembodiment, the memory store 145 is located external to the driver'slicense parser 100, such as at a server 190. In one embodiment, theserver 190 is optionally coupled with the driver's license parser 100and/or the client 155 via wire and/or wirelessly. In one embodiment, abusiness entity controls the server 210. The server 210, in oneembodiment, is capable of uploading updates to the driver's licenseparser 100.

The comparer 120 is configured for comparing the parsed data 112 withrequirements of a loyalty program enrollment policy 150 to determinewhat information of the parsed data 112 falls within the loyalty programenrollment policy 150. Examples of requirements of the loyalty programenrollment policy 150 include, but are not limited to, restrictions onthe residency and age (minors) of the customer. For example, a retailstore may want to only offer its loyalty card to inner city residents orto non-minors. The loyalty program enrollment policy 150 is drafted toinclude the retailer's restrictions. The comparer 120 will determinewhat information of the parsed data 112 is within the restrictionsimposed within the loyalty program enrollment policy 150, and will alsodetermine the information of the parsed data 112 that falls outside ofthese restrictions. For example, the bar code of a 16 year old'sdriver's license is scanned. The loyalty program enrollment policy 150includes a restriction that only those 18 years old and older mayreceive an offer to be registered in the retailer's loyalty program.Thus, the 16 year old's customer profile would include information (thatof being 16 years old instead of the required age of 18 years old) thatwould fall outside of the requirements of the loyalty program enrollmentpolicy 150.

The customer profile validity determiner 125 is configured for, based onthe comparing performed by the comparer 120, determining a validity ofthe customer profile. The customer profile is that information that isassociated with the customer, garnered from the scanned bar code of thecustomer's driver's license (and/or, in another embodiment, which thecustomer entered into a customer-facing device. It should be appreciatedthat the customer-facing device may be a device located at a store inwhich the customer is shopping, or may be coupled via wire and/orwirelessly with a mobile device (e.g., tablet, phone, laptop computer,etc.) and/or a desktop computer). The customer profile validitydeterminer 125 will determine that the customer profile is “valid” ifthe parsed data 112 does not fall outside of the restrictions placedinto the loyalty program enrollment policy 150.

The form populator 130 is configured for, if the customer profile isdetermined to be valid, populating at least one form with the parseddata 112 to achieve at least one populated form 165.

The memory store 145 is configured for storing the parsed data 112 andthe loyalty program enrollment policy 150. In one embodiment, the memorystore 145 is a data storage unit, such as the data storage unit 412 ofFIG. 4.

The form sender 180 is configured for sending the at least one populatedform 165 to a transmitter 215 (see FIG. 2) that is coupled with thedriver's license parser 100.

In one embodiment, the loyalty program savings offer generator 175 isconfigured for, if the customer profile is determined to be valid, andbased upon the customer profile of the customer, generating a loyaltyprogram savings offer for the customer. This loyalty program savingsoffer is any predetermined savings, such as, but not limited to, thefollowing examples: 50% off any item with a purchase of any full-priceditem over $500; the retail store will pay the taxes on any purchaseoccurring over the week-end; and 10% off all items when purchased beforethe current month ends.

The offer sender 180 is configured for sending the loyalty programsavings offer to the transmitter that is coupled with the driver'slicense parser 100 and the client 155.

FIG. 2 shows a system 200 for automatically populating a form usingscanned information from a bar code of a driver's license. The system200 includes the following: the driver's license parser 100; a receiver205; a processor 210; a transmitter 215; a bar code scanner 185; and amemory store 145. The system is shown coupled with the client 155, whichincludes the POS station 160.

Example Methods of Operation

The following discussion sets forth in detail some example methods ofoperation of embodiments. With reference to FIGS. 1-3, flow diagrams ofmethod 300 illustrates an example procedure used by various embodiments.Method 300 includes some procedures that, in various embodiments, arecarried out by a processor under the control of computer-readable andcomputer-executable instructions. In various embodiments, thesecomputer-readable and computer-executable instructions are described as“code segments”, and presented separately (e.g., first codes segment,second code segment, etc.) to describe such instructions. In thisfashion, procedures described herein and in conjunction with these flowdiagrams, alone or in combination, are, or may be, implemented using acomputer, in various embodiments. The computer-readable andcomputer-executable instructions can reside in any tangible computerreadable storage media. Some non-limiting examples of tangible computerreadable storage media include random access memory, read only memory,magnetic disks, and optical disks, solid-state disks, any or all ofwhich may be employed within a virtualization infrastructure. Thecomputer-readable and computer-executable instructions, which reside ontangible computer readable storage media, are used to control or operatein conjunction with, for example, one or some combination of processorsof a virtual machine. It is appreciated that the processor(s) may bephysical or virtual or some combination (it should also be appreciatedthat a virtual processor is implemented on physical hardware). Althoughspecific procedures are disclosed in method 300, such procedures areexamples. That is, embodiments are well suited to performing variousother procedures or variations of the procedures recited in method 300,alone or in combination. Likewise, in some embodiments, the proceduresin method 300, alone or in combination, may be performed in an orderdifferent than presented and/or not all of the procedures described inone or more of these flow diagrams may be performed. It is furtherappreciated that procedures described in method 300, alone or incombination, may be implemented in hardware, or a combination ofhardware with firmware and/or software.

FIG. 3 is a flow diagram of a method 300 for automatically populating aform using scanned information from a bar code of a driver's license, inaccordance with an embodiment. Although specific procedures aredisclosed in method 300, embodiments are well suited to performingvarious other procedures or variations of the procedures recited inmethod 300. It is appreciated that the procedures in method 300 may beperformed in an order different than presented, that not all of theprocedures in method 300 may be performed, and that additionalprocedures to those illustrated and described may be performed. All of,or a portion of, the procedures described by method 300 can beimplemented by a processor or computer system executing instructionswhich reside, for example, on computer-usable/readable media. Thefollowing discussion of method 300 references FIGS. 1-4 unlessspecifically noted otherwise.

At step 305 of method 300, in one embodiment and as described herein,data from a scanned bar code of a driver's license of a customer isaccessed.

At step 310 of method 300, in one embodiment and as described herein,the accessed data is parsed to achieve parsed data, wherein the parseddata represents a customer profile of said customer.

At step 315 of method 300, in one embodiment and as described herein,the parsed data 112 is caused to be stored. In one embodiment, thisoccurs at the memory store 145 residing at the driver's license parser100.

At step 320 of method 300, in one embodiment and as described herein,the parsed data 112 is compared with requirements of a loyalty programenrollment policy 150 to determine what information of the parsed data112 falls within the loyalty program enrollment policy 150.

At step 325 of method 300, in one embodiment and as described herein,based on the comparing, a validity of the customer profile isdetermined.

At step 330 of method 300, in one embodiment and as described herein, ifthe customer profile is determined to be valid, at least one form withthe parsed data 112 is populated to achieve at least one populated form165. In one embodiment, a pre-approved loyalty program form ispopulated. In another embodiment, a credit form is populated.

At step 335 of method 300, in one embodiment and as described herein,the at least one populated form 165 is sent to the point of servicestation 160.

At step 340 of method 300, in one embodiment and as described herein,the at least one populated form 165 is sent to an email address of thecustomer.

At step 345 of method 300, in one embodiment and as described herein, ifthe customer profile is determined to be valid, then a loyalty programsavings offer is generated.

Example Computer System

With reference now to FIG. 4, all or portions of some embodimentsdescribed herein are composed of computer-readable andcomputer-executable instructions that reside, for example, incomputer-usable/computer-readable storage media of a computer system.That is, FIG. 4 illustrates one example of a type of computer (computersystem 400) that can be used in accordance with or to implement variousembodiments which are discussed herein. It is appreciated that computersystem 400 of FIG. 4 is only an example and that embodiments asdescribed herein can operate on or within a number of different computersystems including, but not limited to, general purpose networkedcomputer systems, embedded computer systems, routers, switches, serverdevices, client devices, various intermediate devices/nodes, stand alonecomputer systems, distributed computer systems, media centers, handheldcomputer systems, multi-media devices, and the like. Computer system 400of FIG. 4 is well adapted to having peripheral non-transitorycomputer-readable storage media 402 such as, for example, a floppy disk,a compact disc, digital versatile disc, other disc based storage,universal serial bus “thumb” drive, removable memory card, and the likecoupled thereto.

System 400 of FIG. 4 includes an address/data bus 404 for communicatinginformation, and a processor 406A coupled with bus 404 for processinginformation and instructions. As depicted in FIG. 4, system 400 is alsowell suited to a multi-processor environment in which a plurality ofprocessors 406A, 406B, and 406C are present. Conversely, system 400 isalso well suited to having a single processor such as, for example,processor 406A. Processors 406A, 406B, and 406C may be any of varioustypes of microprocessors. System 400 also includes data storage featuressuch as a computer usable volatile memory 408, e.g., random accessmemory (RAM), coupled with bus 404 for storing information andinstructions for processors 406A, 406B, and 406C.

System 400 also includes computer usable non-volatile memory 410, e.g.,read only memory (ROM), coupled with bus 404 for storing staticinformation and instructions for processors 406A, 406B, and 406C. Alsopresent in system 400 is a data storage unit 412 (e.g., a magnetic oroptical disk and disk drive) coupled with bus 404 for storinginformation and instructions. System 400 also includes an optionalalphanumeric input device 414 including alphanumeric and function keyscoupled with bus 404 for communicating information and commandselections to processor 406A or processors 406A, 406B, and 406C. System400 also includes an optional cursor control device 416 coupled with bus404 for communicating user input information and command selections toprocessor 406A or processors 406A, 406B, and 406C. In one embodiment,system 400 also includes an optional display device 418 coupled with bus404 for displaying information.

Referring still to FIG. 4, optional display device 418 of FIG. 4 may bea liquid crystal device, cathode ray tube, plasma display device orother display device suitable for creating graphic images andalphanumeric characters recognizable to a user. Optional cursor controldevice 416 allows the computer user to dynamically signal the movementof a visible symbol (cursor) on a display screen of display device 418and indicate user selections of selectable items displayed on displaydevice 418. Many implementations of cursor control device 416 are knownin the art including a trackball, mouse, touch pad, joystick or specialkeys on alphanumeric input device 414 capable of signaling movement of agiven direction or manner of displacement. Alternatively, it will beappreciated that a cursor can be directed and/or activated via inputfrom alphanumeric input device 414 using special keys and key sequencecommands. System 400 is also well suited to having a cursor directed byother means such as, for example, voice commands. System 400 alsoincludes an I/O device 420 for coupling system 400 with externalentities. For example, in one embodiment, I/O device 420 is a modem forenabling wired or wireless communications between system 400 and anexternal network such as, but not limited to, the Internet.

Referring still to FIG. 4, various other components are depicted forsystem 400. Specifically, when present, an operating system 422,applications 424, modules 726, and data 428 are shown as typicallyresiding in one or some combination of computer usable volatile memory408 (e.g., RAM), computer usable non-volatile memory 410 (e.g., ROM),and data storage unit 412. In some embodiments, all or portions ofvarious embodiments described herein are stored, for example, as anapplication 424 and/or module 426 in memory locations within RAM 408,computer-readable storage media within data storage unit 412, peripheralcomputer-readable storage media 402, and/or other tangiblecomputer-readable storage media.

1. An article of manufacture, which comprises a computer readable mediumhaving stored therein a computer program for automatically populating aform using information from a scanned bar code of a driver's license,said computer program comprising: a first code segment which, whenexecuted on a computer, accesses data from a scanned bar code of adriver's license of a customer; a second code segment which, whenexecuted on said computer, parses said data to achieve parsed data,wherein said parsed data represents a customer profile of said customer;a third code segment which, when executed on said computer, causes saidparsed data to be stored; a fourth code segment which, when executed onsaid computer, compares said parsed data with requirements of a loyaltyprogram enrollment policy to determine what information of said parseddata falls within said loyalty program enrollment policy; a fifth codesegment which, when executed on said computer, based on said comparing,determines a validity of said customer profile; and a sixth code segmentwhich, when executed on a computer, if said customer profile isdetermined to be valid, populates at least one form with said parseddata to achieve at least one populated form.
 2. The article ofmanufacture of claim 1, wherein said sixth code segment of said computerprogram comprises: a seventh code segment which, when executed on saidcomputer, populates a pre-approved loyalty program form.
 3. The articleof manufacture of claim 1, wherein said sixth code segment of saidcomputer program comprises: an eighth code segment which, when executedon said computer, populates a pre-approved credit account applicationform.
 4. The article of manufacture of claim 1, wherein said computerprogram further comprises: a ninth code segment which, when executed onsaid computer, sends said at least one populated form to a point ofservice station.
 5. The article of manufacture of claim 1, wherein saidcomputer program further comprises: a tenth code segment which, whenexecuted on said computer, sends said at least one populated form to anemail address of said customer.
 6. The article of manufacture of claim1, wherein said computer program further comprises: an eleventh codesegment which, when executed on said computer, if said customer profileis determined to be valid, generates a loyalty program savings offer forsaid customer.
 7. A driver's license parser for automatically populatinga form using information from a scanned bar code of a driver's license,said driver's license parser comprising: a data accessor coupled with acomputer, said data accessor configured for accessing data from ascanned bar code of a driver's license of a customer; a data parsercoupled with said computer, said data parser configured for parsing saiddata to achieve parsed data, wherein said parsed data represents acustomer profile of said customer; a parsed data storer coupled withsaid computer, said parsed data storer configured for causing saidparsed data to be stored; a comparer coupled with said computer, saidcomparer configured for comparing said parsed data with requirements ofa loyalty program enrollment policy to determine what information ofsaid parsed data falls within said loyalty program enrollment policy; acustomer profile validity determiner coupled with said computer, saidcustomer profile validity determiner configured for, based on saidcomparing, determining a validity of said customer profile; and a formpopulator coupled with said computer, said form populator configuredfor, if said customer profile is determined to be valid, populating atleast one form with said parsed data to achieve at least one populatedform.
 8. The driver's license parser of claim 7, further comprising: amemory store coupled with said computer, said memory store configuredfor storing said parsed data and said loyalty program enrollment policy.9. The driver's license parser of claim 7, further comprising: a formsender coupled with said computer, said form sender configured forsending said at least one populated form to a transmitter coupled withsaid driver's license parser.
 10. The driver's license parser of claim7, further comprising: a loyalty program savings offer generator coupledwith said computer, said loyalty program savings offer generatorconfigured for, if said customer profile is determined to be valid, andbased upon said customer profile of said customer, generating a loyaltyprogram savings offer for said customer.
 11. The driver's license parserof claim 7, wherein said form populator comprises: a loyalty programform populator configured for populating a pre-approved loyalty programform.
 12. The driver's license parser of claim 7, wherein said formpopulator comprises: a credit account form populator configured forpopulating a pre-approved credit account application form.
 13. A systemfor automatically populating a form using information from a scanned barcode of a driver's license, said system comprising: a receiverconfigured for receiving information from a scanned bar code of adriver's license of a customer; a memory device configured for storingparsed data and a loyalty program enrollment policy; a processorconfigured for: accessing data from a scanned bar code of a driver'slicense of a customer; parsing said data to achieve parsed data, whereinsaid parsed data represents a customer profile of said customer; causingsaid parsed data to be stored; comparing said parsed data withrequirements of a loyalty program enrollment policy to determine whatinformation of said parsed data falls within said loyalty programenrollment policy; based on said comparing, determining a validity ofsaid customer profile; if said customer profile is determined to bevalid, populating at least one form with said parsed data to achieve atleast one populated form; and a transmitter configured for transmittingsaid populated form to a client.
 14. The system of claim 13, whereinsaid populated form comprises a pre-approved loyalty form program. 15.The system of claim 13, wherein said populated form comprises apre-approved credit account application form.
 16. The system of claim13, wherein said processor is further configured for: if said customerprofile is determined to be valid, and based upon said customer profileof said customer, generating a loyalty program savings offer for saidcustomer.
 17. The system of claim 16, wherein said processor is furtherconfigured for: sending said loyalty program savings offer to atransmitter for sending to a client.